Apparatus and method of coordinating operation action of robot software component

ABSTRACT

Provided are an apparatus and a method of controlling the execution of components without an additional port or messaging for applying the dependency among the components. The apparatus comprises: a profile analyzing unit analyzing execution dependency information of components defined in an execution coordination profile; a component managing unit arranging the components in accordance with the execution sequence of the components caused by the execution dependency information; an execution coordination managing unit determining whether or not each of the components executes the operation on the basis of the execution dependency information of the corresponding component managed by the execution coordination units allocated to the components, respectively; and an operation executing unit executing the operation of each of the components in accordance with the determination result of the execution coordination manager.

CROSS REFERENCE TO RELATED APPLICATION

This application claims the benefit of Korean Patent Application No.10-2009-0127073, filed on Dec. 18, 2009 and Korean Patent ApplicationNo. 10-2010-0015262, filed on Feb. 19, 2010, which are herebyincorporated by reference in its entirety into this application.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates to an apparatus and a method ofcoordinating an operation action of a robot software component, and moreparticularly, to an apparatus and a method of designating, in anapplication operated in a robot software component framework, theexecution order among components constituting the correspondingapplication and arranging and execute an operation so as to perform akey operation of a corresponding component in accordance with thedesignated order.

2. Description of the Related Art

Presently, the operation of a robot software component employs a schemein which one thread is allocated to one component, such as open robotcontrol software (OROCOS) or a robot technology component (RTC). Ofcourse, in addition to the scheme, a scheme in which one application hasone process, such as openJAUS, a scheme in which one thread processesthe operations of a plurality of components having the same cycle, suchas an open platform for robotic services (OPROS) component frame work,and the like are employed.

As such, under an environment where many components are operated, thecomponents may be dependent on each other.

For example, as shown in FIG. 1, it is assumed that a pedestriandetection component 14 that detects a pedestrian through datatransferred from an image sensor component 10 and a laser sensorcomponent 12 is configured.

The pedestrian detection component 14 should use both results from twosensor components 10 and 12 in accordance with its characteristic. Ifonly one data exists, when the pedestrian detection component 14 isconfigured in a scheme in which the corresponding data is removed, thepedestrian detection component 14 needs to be executed after receivingthe data from the image sensor component 10 and the laser sensorcomponent 12 every execution cycle. When the pedestrian detectioncomponent 14 is executed earlier than one between the sensor components10 and 12, a value in the corresponding execution cycle is removed.Meanwhile, when waiting until all data are inputted, the pedestriandetection component 14 does not process the components in thecorresponding execution cycle but processes the components in the nextexecution cycle.

As described above, the pedestrian detection component 14 is dependenton the action of the image sensor component 10 and the laser sensorcomponent 12.

In the prior art, when the components are dependent on each other, adependent component among components processed in different threadscontinuously checks a predetermined variable indicating a state of apreceding component. According to the checking result, when thedependent component reaches a predetermined state, the dependentcomponent performs its own operation. Meanwhile, when componentsprocessed by different processes are dependent on each other, thedependent components are configured to react to a predetermined eventmessage through network messaging or interprocess communication (IPC).

However, in all of the methods, the dependent component should acquirethe state of the preceding component or process a particular eventmessage of the preceding component.

For the dependency, a component developer should include thecorresponding mechanism when preparing the component. The precedingcomponent should have an extra variable so as to allow the componentdepending on itself to a processing state of the preceding componentitself. The preceding component should be prepared to notify its ownaction state by establishing a predetermined port that enables accessingthe corresponding variable or through messaging.

The method cannot be applied when the component developer does not knowwhether or not the component prepared by the component developer will beused in dependent application afterwards. Even though the component isprepared under the dependent environment, the component cannot be usedunder an environment other than a predetermined environment.

For example, when the pedestrian detection component is configured asshown in FIG. 1 by using the prior art, the image sensor component 10used by the pedestrian detection component 14 should previously knowthat a component which is dependent on the corresponding componentexists during a development stage. Further, the image sensor component10 should be configured to have an additional port that allows anothercomponent to know the execution state of the image sensor component 10,which is other than a port that transfers an image to another componentor to notify the completion of the operation through messaging.

SUMMARY OF THE INVENTION

The present invention has been made in an effort to overcome a problemof the prior art described above and provide an apparatus and a methodof defining the dependency among components in a runtime without anadditional port or messaging for applying the dependency among thecomponents, setting the execution sequence of the components inaccordance with the defined dependency, and controlling the execution ofcomponents which are influenced depending on the execution result of thecomponent at the execution stage.

An embodiment of the present invention provides an apparatus ofcoordinating an operation act of a robot software component thatcomprises: a profile analyzing unit analyzing execution dependencyinformation of components defined in an execution coordination profile;a component managing unit arranging the components in accordance with aexecution sequence of the components based on the execution dependencyinformation; an execution coordination managing unit determining whetheror not each of the components can execute the operation on the basis ofthe execution dependency information of the corresponding componentmanaged by the execution coordination units allocated to the components,respectively; and an operation executing unit executing the operation ofeach of the components in accordance with the determination result ofthe execution coordination managing unit.

The execution sequence of the components may be set based on theexecution dependency information in a runtime.

The component managing unit may allocate the execution coordinationunits to the components and register the execution coordination units inthe execution coordination managing unit.

The component managing unit may arrange the components on an operationtable of the operation executing unit in sequence on the basis of theexecution dependency information.

The operation executing unit may have an operation table where two ormore components and execution coordination units, which are allocated totwo or more components respectively to manage the execution dependencyinformation of the corresponding component, are arranged.

The operation executing unit may verify whether or not all precedingoperations of the corresponding component are executed through theexecution coordination managing unit before executing the operation ofeach component.

The operation executing unit may execute the operation of thecorresponding component when all the preceding operations of thecorresponding component are executed.

The operation executing unit may suspend the operation of thecorresponding component and execute next operation when all thepreceding operations of the corresponding component are not executed ornot yet completed.

The operation executing unit may update a state of condition of theexecution coordination unit of the corresponding component through theexecution coordination manager when the operations of all the componentsare executed.

Another embodiment of the present invention provides a method ofcoordinating an operation action of a robot software component thatcomprises: analyzing execution dependency information of componentsdefined in an execution coordination profile by a profile analyzingunit; arranging the components in accordance with the execution sequenceof the components based on the execution dependency information by acomponent managing unit; determining whether or not each of thecomponents can execute the operation on the basis of the executiondependency information of the corresponding component managed by theexecution coordination units allocated to the components, respectivelyby an execution coordination managing unit; and executing the operationof each of the components in accordance with the determination result ofthe execution coordination managing unit by an operation executing unit.

The execution sequence of the components may be set based on theexecution dependency information in a runtime.

The execution coordination units may be allocated to the components,respectively by the component managing unit and registered in theexecution coordination managing unit.

The arranging of the components may arrange the components on anoperation table of the operation executing unit in sequence on the basisof the execution dependency information.

The executing of the operation may verify whether or not all precedingoperations of the corresponding component are executed through theexecution coordination managing unit before executing the operation ofeach component.

The executing of the operation may execute the operation of thecorresponding component when all the preceding operations of thecorresponding component are executed.

The executing of the operation may suspend the operation of thecorresponding component and execute next operation when all thepreceding operations of the corresponding component are not executed ornot yet completed.

The method may further comprise updating a condition state of theexecution coordination unit of the corresponding component through theexecution coordination managing unit when the operations of all thecomponents are executed, by the operation executing unit.

According to the embodiments of the present invention, it is possible todefine the dependency among components in a runtime in various componentapplications.

Accordingly, it is possible to prevent the malfunction of the componentsdue to an execution sequence.

It is possible to optimize the application of the component by matchingthe arrangement of the components with an execution flow expected whileconfiguring the application.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram for describing a prior art;

FIG. 2 is a block diagram for describing an apparatus of coordinating anoperation action of a robot software component according to anembodiment of the present invention;

FIG. 3 is a flowchart for describing a method of coordinating anoperation action of a robot software component according to anembodiment of the present invention;

FIG. 4 is an example of an execution coordination profile definingexecution dependency of a component as an example adopted in thedescription of FIG. 3; and

FIG. 5 is a diagram for describing a process of rearranging an operationdepending on execution dependency of a component as an example adoptedin the description of FIG. 3.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

Hereinafter, an apparatus and a method of coordinating an operationaction of a robot software component according to an exemplaryembodiment of the present invention will be described with reference tothe accompanying drawings. The terms and words used in the presentspecification and claims should not be interpreted as being limited totypical meanings or dictionary definitions. Accordingly, exemplaryembodiments disclosed in the specification and configurations shown inthe accompanying drawings are just the most preferred embodiment, butare not limited to the spirit and scope of the present invention.Therefore, at this application time, it will be appreciated that variousequivalents and modifications may be included within the spirit andscope of the present invention.

FIG. 2 is a block diagram for describing an apparatus of coordinating anoperation action of a robot software component according to anembodiment of the present invention.

The robot software component operation action coordinating apparatusshown in FIG. 2 comprises a profile analyzing unit 22, a componentmanaging unit 24, an execution coordination managing unit 26, and anoperation executing unit 28.

The profile analyzing unit 22 analyzes execution dependency informationof components 42, 44, and 46 defined in an execution coordinationprofile 20. The profile analyzing unit 22 transfers the analysis resultto the component managing unit 24. The execution coordination profile 20includes data clearly describing the dependency among the components 42,44, and 46 by a component application producer.

The component manager 24 arranges, in sequence, the components on anoperation table 30 of the operation execution unit 28 in accordance withthe execution sequence of the components 42, 44, and 46 caused by theexecution dependency information. Preferably, the execution sequence ofthe components 42, 44, and 46 is set based on the execution dependencyinformation in a runtime. Herein, the runtime may represent a timecorresponding to an operation cycle of the operation executing unit 28.The component manager 24 allocates execution coordination units 52, 54,and 56 to the components 42, 44, and 46, respectively and registers themin the execution coordination managing unit 26. Each of the executioncoordination units 52, 54, and 56 manages the execution dependencyinformation of the corresponding component.

The execution coordination managing unit 26 determines whether or noteach of the components 42, 44, and 46 can execute the operation on thebasis of the execution dependency information of the correspondingcomponent managed by the execution coordination units 52, 54, and 56allocated to the components 42, 44, and 46, respectively. That is, theexecution coordination managing unit 26 receives a question whether eachof the components 42, 44, and 46 can execute the operation from theoperation executing unit 28, and determines whether or not eachcomponent can execute the operation and notifies the determinationresult to the operation executing unit 20.

The operation executing unit 28 executes the operation of each of thecomponents 42, 44, and 46 in accordance with the determination result ofthe execution coordination managing unit 26. The operation executingunit 28 has an operation table 30. Two or more components 42, 44, and 46and the execution coordination units 52, 54, and 56 representing theexecution dependency information of the corresponding component at thecomponent execution stage by being allocated to each of two or morecomponents are arranged in the operation table 30. The operationexecuting unit 28 verifies whether or not a component which theoperation execution unit 28 wants to execute conforms to an executioncondition to the execution coordinate managing unit 26 every operationcycle. After verification, the operation executing unit 28 executes theoperation of each of the components 42, 44, and 46, and updates acondition depending on the execution result and rearranges the operationsequence. That is, the operation executing unit 28 verifies whether ornot all preceding operations of the corresponding component are normallyperformed through the execution coordination managing unit 26 beforeexecuting the operation of each component. When all of the precedingoperations of the corresponding component are normally performed, theoperation executing unit 28 performs the operation of the correspondingcomponent. When all of the preceding operations of the correspondingcomponent are not normally executed or are not yet completed, theoperation executing unit 28 suspends the operation of the correspondingcomponent and executes the next operation. The operation executing unit28 updates a state of condition of an execution coordination unit of thecorresponding component through the execution coordination managing unit26 when all the operations of the component are normally executed.

In FIG. 2, although only one operation executing unit 28 is shown, itmay be regarded that a plurality of operation executing units 28 areprovided.

Subsequently, a method of coordinating an operation action of a robotsoftware component according to an embodiment of the present inventionwill be described in detail with reference to a flowchart of FIG. 3.FIG. 4 is an example of an execution coordination profile definingexecution dependency of a component as an example adopted in thedescription of FIG. 3. FIG. 5 is a diagram for describing a process ofrearranging an operation depending on execution dependency of acomponent as an example adopted in the description of FIG. 3.

First, describing an execution coordination profile (S10) is performed.An application developer may define the execution coordination profile20 in the form of a file, and the like. A content defined in theexecution coordination profile 20 represents dependency amongcomponents. In the case of the execution coordination profile shown inFIG. 4, a component “SubTest” is defined to be dependent on a component“HelloMaker” and components “MessagePrinter”. That is, the component“HelloMaker” 42 and the component “MessagePrinter” 44 of FIG. 2 shouldbe executed earlier than the component “SubTest” 46.

Next, analyzing the execution coordination profile (S20) is performed. Aprofile analyzing unit 22 analyzes the execution coordination profile 20and transfers information indicating a component dependency relationshipto a component managing unit 22.

Next, registering an execution coordination unit (S30) is performed. Thecomponent managing unit 24 loads components 42, 44, and 46 and allocatesexecution coordination units 52, 54, and 56 to the components 42, 44,and 46, respectively. Herein, the components 42, 44, and 46 are randomlyloaded regardless of the execution dependency relationship. Since therelationships among the execution coordination units 52, 54, and 56cannot be connected with each other, the component managing unit 24registers the execution coordination units 52, 54, and 56 to theexecution coordination managing unit 26 by using component informationas a key value. When each of the execution coordination units 52, 54 and56 are registered, the connections among the execution coordinationunits 52, 54, and 56 are updated depending on the component dependencyrelationship. For example, when the component 46 is the first loaded,the execution coordination units 52 and 54 are not generated while thecomponents 42 and 44 on which the component 46 depends are not yetloaded.

As a result, it is impossible to set the relationship between theexecution coordination unit 56 and other execution coordination units 52and 54. Therefore, the component managing unit 24 registers the firstlygenerated execution coordination unit 56 in the execution coordinationmanaging unit 26. Thereafter, when the component 44 is loaded and theexecution coordination unit 54 is generated, the component managing unit24 finds that the execution coordination unit 56 depending on theexecution coordination unit 54 is registered in the executioncoordination managing unit 26. As a result, the component managing unit24 adds the execution coordination unit 54 to the execution coordinationunit 56 as a prerequisite and adds the execution coordination unit 56 tothe execution coordination unit 54 as a subsequent operation.Thereafter, the operation is repetitively performed at the time ofloading other components and finally, a dependency relationship whichthe application developer requires is constructed.

Next, arranging components (S40) is performed. The component managingunit 24 arranges the components on the operation table 30 of theoperation executing unit 28 in sequence in accordance with the executionsequence of the components.

Next, inquiring an operation execution condition (S50) is performed. Theoperation executing unit 28 performs the components 42, 44, and 46 to beperformed in the operation table 30 every operation cycle one by one inaccordance with the arrangement order. While the operation executingunit 28 performs the operations of the components 42, 44, and 46, theoperation executing unit 28 inquires whether or not all of the precedingoperations of the corresponding component are normally performed to theexecution coordination managing unit 26 and thereafter, receives a replyto the inquiry from the execution coordination managing unit 26.

Next, executing the operation (S60) is performed. When all of thepreceding operations of the corresponding component are normallyperformed, the operation executing unit 28 performs the operation of thecorresponding component. When all of the preceding operations of thecorresponding component are not normally executed or are not yetexecuted, the operation executing unit 28 suspends the operation of thecorresponding component and executes the next operation.

For example, as shown in FIG. 5, it is assumed that a component B 86that is arranged in an operation table (not shown) of an operationexecuting unit 1 60 is dependent on a component E 82 that is arranged inan operation table (not shown) of an operation executing unit 2 70. Itis assumed that the component E 82 is dependent on a component A 80 thatis arranged in an operation table (not shown) of the operation executingunit 1 60. In FIG. 5, an operation cycle of the operation executing unit1 60 has a time as long as all of the operations A, B, C, and D can beexecuted. When the component B 86 should be executed after the operationof the component A 80 is executed in the operation executing unit 1 60,if the component E 82 on which the component B 86 depends does not yetterminate the operation, a component C 88 moves to a location of “84”.As a result, the operation of the component C 88 is executed earlierthan the operation of the component B 86. By this configuration, theblocked component B 86 prevents the execution of other operations frombeing disturbed so as to improve runtime performance. Meanwhile, if theoperation of the component B 86 is not yet terminated until an operationof a final component D 90 is terminated on the operation table of theoperation executing unit 1 60, the operation executing unit 1 60determines to process the operation of the component B 86 at the nextcycle without waiting any longer.

Next, updating the execution condition (S70) is performed. The operationexecuting unit 28 updates the states of condition of the executioncoordination units 52, 54, and 56 of the components through theexecution coordination managing unit 26 when all of the operations ofthe components 42, 44, and 46 are normally executed.

For example, when the operation of the component 42 is normallyexecuted, the operation executing unit 28 updates one of prerequisitesof the execution coordination unit 56 which is dependent on theexecution coordination unit 52 to be satisfied. The executioncoordination unit 56 does not satisfy the execution condition before theoperation of the component 44 which is another prerequisite is normallyexecuted. After the operation of the component 44 is executed, theexecution coordination unit 56 satisfies the execution condition and isset to execute the operation of the component 46. When the executioncondition is satisfied to execute the operation of the correspondingcomponent 46, the execution condition of the execution coordination unit56 related to the corresponding component 46 is cancelled again.

Thereafter, the execution coordination unit 56 waits for the precedingcomponents 42 and 44 to be executed again.

While the present invention has been described in connection with whatis presently considered to be practical exemplary embodiments, it is tobe understood that the invention is not limited to the disclosedexemplary embodiments, but, on the contrary, is intended to covervarious modifications and equivalent arrangements included within thespirit and scope of the appended claims. Accordingly, the actualtechnical protection scope of the present invention must be determinedby the spirit of the appended claims.

1. An apparatus of coordinating an operation action of a robot softwarecomponent, comprising: a profile analyzing unit analyzing executiondependency information of components defined in an executioncoordination profile; a component managing unit arranging the componentsin accordance with an execution sequence of the components based on theexecution dependency information; an execution coordination managingunit determining whether or not each of the components executes theoperation on the basis of the execution dependency information of thecorresponding component managed by an execution coordination unitsallocated to each of the components; and an operation executing unitexecuting the operation of each of the components in accordance with thedetermination result of the execution coordination managing unit.
 2. Theapparatus of claim 1, wherein the execution sequence of the componentsis set based on the execution dependency information in a runtime. 3.The apparatus of claim 1, wherein the component managing unit allocatesthe execution coordination units to the components and registers theexecution coordination units in the execution coordination managingunit.
 4. The apparatus of claim 1, wherein the component managing unitarranges the components on an operation table of the operation executingunit in sequence.
 5. The apparatus of claim 1, wherein the operationexecuting unit has an operation table where two or more components andexecution coordination units allocated to two or more componentsrespectively to manage the execution dependency information of thecorresponding component are arranged.
 6. The apparatus of claim 1,wherein the operation executing unit verifies whether or not allpreceding operations of the corresponding component are executed throughthe execution coordination managing unit before executing the operationof each component.
 7. The apparatus of claim 1, wherein the operationexecuting unit executes the operation of the corresponding componentafter all the preceding operations of the corresponding component areexecuted.
 8. The apparatus of claim 1, wherein the operation executingunit suspends the operation of the corresponding component and executesnext operation when all the preceding operations of the correspondingcomponent are not executed or not yet completed.
 9. The apparatus ofclaim 1, wherein the operation executing unit updates a state ofcondition of the execution coordination unit of the correspondingcomponent through the execution coordination managing unit when theoperations of all the components are executed.
 10. A method ofcoordinating an operation action of a robot software component,comprising: analyzing execution dependency information of componentsdefined in an execution coordination profile by a profile analyzingunit; arranging the components in accordance with the execution sequenceof the components based on the execution dependency information by acomponent managing unit; determining whether or not each of thecomponents executes the operation on the basis of the executiondependency information of the corresponding component managed by anexecution coordination units allocated to each of the components, by anexecution coordination managing unit; and executing the operation ofeach of the components in accordance with the determination result ofthe execution coordination managing unit by an operation executing unit.11. The method of claim 10, wherein the execution sequence of thecomponents is set based on the execution dependency information in aruntime.
 12. The method of claim 10, wherein the execution coordinationunits are allocated to each of the components, by the component managingunit and registered in the execution coordination managing unit.
 13. Themethod of claim 10, wherein the arranging of the components arranges thecomponents on an operation table of the operation executing unit insequence.
 14. The method of claim 10, wherein the executing of theoperation verifies whether or not all preceding operations of thecorresponding component are executed through the execution coordinationmanaging unit before executing the operation of each component.
 15. Themethod of claim 10, wherein the executing of the operation executes theoperation of the corresponding component when all the precedingoperations of the corresponding component are executed.
 16. The methodof claim 10, wherein the executing of the operation suspends theoperation of the corresponding component and executes next operationwhen all the preceding operations of the corresponding component are notexecuted or not yet completed.
 17. The method of claim 10, furthercomprising updating a condition state of the execution coordination unitof the corresponding component through the execution coordinationmanaging unit when the operations of all the components are executed, bythe operation executing unit.